Docs Build status updates of commit 12e1448:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Docs Build status updates of commit 1d49199:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Docs Build status updates of commit 3b9b6e6:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Global effort to fix broken links

@nmetulev
@michael-hawker
@Arlodotexe

The Content & Learning team is fixing broken links on docs.microsoft.com for the rest of H2. This effort will eliminate potential accessibility, security, and usability issues. This PR includes only link fixes and does not change other content. I’d very much appreciate your timely review and feedback on the link changes I’ve suggested. Thanks!

Docs Build status updates of commit 4f06bc6:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Docs Build status updates of commit bcfa296:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Docs Build status updates of commit c05aec7:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Docs Build status updates of commit 9006371:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Docs Build status updates of commit fe8cc01:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Would like to keep our version numbers in our links. Also saw there were some just fenced out. Pointed out many, but still a few left to update. If you need extra assistance finding the new location, @Arlodotexe mind helping the docs folks out for this and #642?

Thanks very much! I appreciate all recommendations and am prepared to commit any link replacements you suggest regarding this PR and future PRs involving this repo! With any luck, you'll be able to locate replacements for the broken links I commented out.

Docs Build status updates of commit 517638f:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Docs Build status updates of commit 5b51462:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Would like to keep our version numbers in our links. Also saw there were some just fenced out. Pointed out many, but still a few left to update. If you need extra assistance finding the new location, @Arlodotexe mind helping the docs folks out for this and #642?

Please let us know if you require any additional edits that will expedite review and merge of this PR. Thank you.

@kturetz Please update your changes based on feedback in PR #646. Thanks.

Docs Build status updates of commit 811b34f:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

@michael-hawker I think this is ready to merge. If not, we can close this PR and I'll have someone else from my team finish the work. Thanks!